InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-04.Z/94-04/text0327.txt

Text File | 1994-04-30 | 9.7 KB | 272 lines

In article <[e-mail]> [e-mail] (Bernard Collins) writes:
>From: [e-mail] (Bernard Collins)
>Subject: Re: FTPd problems - still Re: Small Weekend FTP Server at it again!
>Date: 18 Apr 1994 16:28:56 -0400

>[e-mail] (David R. Downs) writes:
>>I switched to Trumpet and "poof" no problems!  Now, I intend to write FTP Inc.

>Just one question: what version of PCTCP are you using? Have you gotten
>hold of their relatively recent winsock fix? (Oh, that's two questions.
>Sorry)
>--
>Skip Collins

i'm running alun's ftpserver and although it dose crash once in a while i
leave it running all the time and i rarely have any probs. the userlimit thing
though won't be delt with till the next ver (says alun) but i think its the
best i've found for winsock. rember there is always lynix! (if youy have an
extra 50 to 200 megs!)

-Sargon                                  Ftp for windows and winsock files
[e-mail]                        'b61503.student.cwru.edu'
                     "The only perfect science is hindsight."
From [e-mail] Sat Apr 26 21:54:53 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA25059; Thu, 28 Apr 1994 20:31:59 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA14975; Thu, 28 Apr 1994 20:20:25 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 27 Apr 1994 04:54:53 -0700
From: [e-mail] (Paul Smith)
Message-Id: <2pljqd$[e-mail]>
Organization: CRL Dialup Internet Access    [phone]  [login: guest]
Sender: ses
References: <[e-mail]>, <[e-mail]>
Subject: Re: Xwindows for Winsock?

Steve Ratliff ([e-mail]) wrote:
:     On an entirely different subject.  Does anyone know of a PD,
: freeware, or shareware version of a NFS winsock client?

Try Tsoft's NFS client over a DOS stack.  I'm running this NFS
client side by side with trumpet winsock, side by side with
NETBUEI in WFWG 3.11.  It works is the main thing.  For technical
reasons (from the authors) it runs on DOS and a DOS TCP/IP stack
and not under windows on winsock.

polyslo.calpoly.edu:/pub/mdurkin/nfs

    Grabe all versions sort them out after you decided which
    DOS TCP stack you want to run.  I'm running the version
    with the built in Wattcp stack on dis_pkt9, pktmux 2, pktdrv,
    pktdrv.

The tricks of installatoin are as follows on WFWG 3.11, just Windows 3.1
is considerably simpler and a small subset of this:


autoexec.bat - fragments
-------------------------

C:\WIN3\net start
lh c:\win3\pktmux 2 61 /b
REM could not get winpkt to work... if it would have, I might
REM been able to save alittle bit of low mem
REM lh c:\win3\winpkt 0x62 0x61
REM lh c:\win3\winpkt 0x63 0x61
lh c:\win3\pktdrv 62 61 /w10
lh c:\win3\pktdrv 63 61 /w10
set TZ=EDT8EDT
set WATTCP.CFG=c:\winnfs
c:\winnfs\nfsdrvr -s 2 -f 10 -d 3
c:\winnfs\mount -a
REM at this point; mem/d indicates that the max size prog I can run
REM is 514k.  After running WFWG 3.11 running a DOS session and running
REM mem/d again, the max size prog is 479k.  Gettting tighter and
REM tighter.  NOTE: some older windows/DOS progs are unreliable at this
REM amount of low mem.  Some (ABC flow charting) are execption faulting
REM for some of their menu picks/changing printer options...

system.ini fragments
--------------------

[network drivers]
netcard=exp16.dos
transport=ndishlp.sys,*netbeui,dis_pkt9.dos
devdir=C:\WIN3
LoadRMDrivers=Yes

protocol.ini fragments
----------------------


[network.setup]
version=0x3110
netcard=ms$ee16,1,MS$EE16,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,NETBEUI
lana0=ms$ee16,1,ms$netbeui
lana1=ms$ee16,1,ms$ndishlp

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$EE16]
DriverName=EXP16$
IRQ=10
IOADDRESS=0x350
IOCHRDY=Late
TRANSCEIVER=Thin Net (BNC/COAX)

[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=MS$EE16

[NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=MS$EE16
LANABASE=0

[pktdrv]
DriverName=PKTDRV$
bindings=MS$EE16
intvec=0x61
novell=no

...
From [e-mail] Wed Apr 27 04:37:36 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA28736; Thu, 28 Apr 1994 21:01:54 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA12503; Thu, 28 Apr 1994 20:37:37 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 27 Apr 1994 08:37:36 EDT (GMT -0400)
From: [e-mail] (Harry M. Kriz)
Message-Id: <[e-mail]>
Organization: Virginia Tech
Sender: ses
Subject: FTP clients miss files

I've just become aware of a problem with my Windows graphical ftp client. I'm
wondering if the problem can be overcome.

I was using WS_FTP to view the directory d:/Softlib/MSLFILES at
ftp.microsoft.com. I was looking for the file ww1000.exe, which contains
vshare.386, a protected mode version of the old DOS share.exe. The file didn't
show up in the list of files presented by WS_FTP.

I then used the ftp client in WinQVT/Net to access the same directory and
issued the get command for the file. I got a copy of the file, so it was
indeed in the directory. (See the file wdl.txt for more information about
available files at ftp.microsoft.com.)

Microsoft warns that you shouldn't issue a dir command for the MSLFILES
directory, as it is very large. I assume that WS_FTP did issue the dir
command, took as many file names as it could and displayed them, and simply
dropped all the rest from the list without warning.

Question:  Is this a problem common to all graphical ftp clients, or is there
a way that the client could warn you that the directory listing is not
complete?

I sent a note to John Junod, author of WS_FTP, and he said he'd be
looking into this further.

--Harry
-----------------------------------------------------------------
Harry M. Kriz      [e-mail]
University Libraries
Virginia Polytechnic Institute & State University (Virginia Tech)
Blacksburg, VA   24061
From [e-mail] Thu Apr 28 17:07:07 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA28744; Thu, 28 Apr 1994 21:01:56 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA13111; Thu, 28 Apr 1994 20:55:09 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 28 Apr 1994 17:07:07 GMT
From: [e-mail] (Georg Schwarz)
Message-Id: <[e-mail]>
Organization: ETH-Zuerich
Sender: ses
Subject: I'd pay for a good TELNET client for winsock

I am looking for a winsock telnet client with a good VT100 or VT220 emulation.
I have tried:

  - trumptel, wich has problems with the emulation
  -QVTnet wich works fine, but comes with a lot of stuff i
    dont use (mail, news..) and cannot be used as
    viewer in a gopher client.
  - MS Telnet wich comes with the Daytona Beta
     wich has problems with the emulation.
  - FTP's telnet client, works great, but only
     with their TCP stack

I am only looking for a telnet client, so if it is bundeled with other stuff
the complete package should not be too expensive.

Any hints?
Thanks in advance

Georg
-------------------------------------------------------------------
Georg Schwarz              Institut fuer Geophysik
[e-mail]     ETH-Hoenggerberg
Voice: [phone]      CH-8093 Zuerich
Fax:   [phone]      Switzerland
-------------------------------------------------------------------
From [e-mail] Thu Apr 28 14:47:04 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA02525; Thu, 28 Apr 1994 21:31:55 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA22249; Thu, 28 Apr 1994 21:10:26 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 28 Apr 1994 14:47:04 GMT
From: [e-mail] (Dave Carey)
Message-Id: <[e-mail]>
Organization: NASA Langley Research Center
Sender: ses
Subject: Windows/NT and winsock


  I have a PC running Windows/NT with a 3c503 card. How do I configure to run
winsock. I have setup several PCs running Windows with Trumpet Winsock and
PCTCP 2.2 and 2.3. I can use whichever software setup is easiest.
 Help!



 Dave C.
From [e-mail] Thu Apr 28 21:31:57 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA02535; Thu, 28 Apr 1994 21:31:57 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA07498; Thu, 28 Apr 1994 21:28:08 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 28 Apr 1994 16:53:38
From: [e-mail] (Axel Kieser)
Message-Id: <[e-mail]>
Organization: TUBerlin/ZRZ
Sender: ses
Subject: wfwg 3.11, winsock, SMC-ethercard +elite16

Hi, I think this is a question which was often answered before, but I haven't
saved the answers and now I need a solution for my problem.

I run WFWG 3.11 without network support and Trumpet-Winsock. I have a SMC
EtherCard Plus Elite 16 and load the drivers wd8003e and winpkt.com before
starting WFWG, no problems.
What have I to do to get WFWG-networking and run winsock.dll, too?
Please send me your protocol.ini-files and the important parts of system.ini
and a short and easy description of what to do.

Please answer by e-mail, too.

Thanks in Advance, Axel